The bash tool needs ctx.abort to handle user cancellation gracefully —
returning partial output through normal truncation. Pure Effect
interruption can't produce a return value (effect-smol's Effect.exit
doesn't consume interrupts). Moving to Effect interruption for bash
requires taking tool dispatch from the AI SDK (forkChild), which is
a separate change.

The task tool passes ctx.abort to sub-sessions. Without a real signal,
bash in sub-sessions can't handle cancellation. Use AbortController +
onInterrupt to fire the signal when the task fiber is interrupted.

Remove Effect.promise wrappers around ctx.ask() in all tools — now
just yield* ctx.ask(...) directly. Update prompt.ts boundary to return
Effect from permission.ask (with orDie). Plugin tool context converts
back to Promise at the boundary. Update all test mocks.

…annel

wrap() in tool.ts already applies Effect.orDie. Tools whose execute
has typed errors (codesearch, webfetch, etc.) still need their own
orDie to satisfy the Def.execute type. Tools with never errors
(edit, multiedit, todo, lsp) had redundant orDie — removed.
Also merge double .pipe() chain in prompt.ts subtask handling.

Close over Truncate.Service in registry layer gen and use
truncate.output() directly instead of the static Truncate.output()
facade. Also convert fromPlugin execute from Effect.promise to
Effect.gen for cleaner service usage.

- FileTime.withLock now accepts () => Effect<T> instead of () => Promise<T>
- edit.ts withLock callback converted from async to Effect.gen, uses
  AppFileSystem.Service, Format.Service, and FileTime.Service directly
- edit/write/apply_patch tools use Bus.Service instead of Bus.publish facade
- write.ts uses Format.Service instead of Format.file facade